-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/integrate-sdk #34
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! Couple questions for you before merging!
|
||
if (!response.ok) { | ||
if (response.code !== 200) { | ||
error(500, 'Unable to fetch arrivals-and-departures-for-stop.'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does the error()
method here function function like an exception? i.e. does it interrupt control flow?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know, I tried it now, and it seems not interrupt the flow, but when I enter the stop route endpoint, the error message appears in the top
https://learn.svelte.dev/tutorial/error-basics
but according to svelte docs the expected error message is shown to the user
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
super cool. I'm excited to see this get used across the codebase. I'm going to merge it now and you can continue adding new support for other endpoints
FYI @tarunsinghofficial - make sure you pull main and do an npm install :) |
This PR contains the integration of the SDK in the arrivalsAndDepartures and stop endpoints